Skip to content

Lily/ClonesPlus: revert breaking change #2110

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 21, 2025

Conversation

TheShovel
Copy link
Contributor

@TheShovel TheShovel commented May 5, 2025

5825ea7
This change breaks projects made with previous versions of the extension. This is was a change in functionality!

One of my projects is affected by this change, because it is built with clones starting with empty local variables in mind. This should be handled differently. I dont know how this was approved. You cant change stuff like this after such a long time of them working this way, without making sure that old projects are unaffected

@github-actions github-actions bot added the pr: change existing extension Pull requests that change an existing extension label May 5, 2025
@SharkPool-SP
Copy link
Collaborator

Well now this ‘breaks’ projects using the new change

@GarboMuffin
Copy link
Member

this is a very unfortuante situation but probably since there hasnt been a desktop app update with this, it can be feasibly reverted, ...

Copy link
Member

@yuri-kiss yuri-kiss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see why not, we can make a separate pull request to make this a new block :), to "fix" the "bug", that SharkPool-SP doesnt want the fix reverted for.

@GarboMuffin GarboMuffin changed the title Revert ClonesPlus breaking change Lily/ClonesPlus: revert breaking change May 21, 2025
@GarboMuffin GarboMuffin merged commit a4d5612 into TurboWarp:master May 21, 2025
4 checks passed
CubesterYT pushed a commit that referenced this pull request May 21, 2025
…riginal (#2123)

context: #2110

re-fixes: #1421

---------

Co-authored-by: DangoCat[bot] <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr: change existing extension Pull requests that change an existing extension
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants